Character data is stored in many of the fields of the data model on
which the UI may search.  Examples include
fsc_account_dim.account_number and
fsc_transaction_dim.transaction_reference_number.

We do not currently
assume that the ETL process will map character data stored in these
fields to uppercase.  The UI also makes no assumptions about the case of
the data entered or stored in the database.  Therefore, comparisons
against these fields often contain WHERE clauses of the form:

   WHERE upper(account_number) = ?

The use of a function in this context renders the index on
account_number useless and can increase execution time by many orders of
magnitude.

As a temporary workaround for the 14AML03 hotfix, function-based indexes
were added to the Oracle DDL.  This will not fix the problem at DB2
sites, nor is it a comprehensive solution, as the same problems could
occur with other columns and it is impractical to put function-based
indexes on all of them.

Operating System and Release Information